home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat2 / standard / sched_getscheduler.z / sched_getscheduler
Encoding:
Text File  |  2001-04-17  |  3.7 KB  |  66 lines
  1.  
  2.  
  3.  
  4. sssscccchhhheeeedddd____ggggeeeettttsssscccchhhheeeedddduuuulllleeeerrrr((((2222))))                                    sssscccchhhheeeedddd____ggggeeeettttsssscccchhhheeeedddduuuulllleeeerrrr((((2222))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_ssss_cccc_hhhh_eeee_dddd_uuuu_llll_eeee_rrrr - get the scheduling policy of a process
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<sssscccchhhheeeedddd....hhhh>>>>
  13.      _iiii_nnnn_tttt _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_ssss_cccc_hhhh_eeee_dddd_uuuu_llll_eeee_rrrr _((((_pppp_iiii_dddd______tttt _p_i_d_))))_;;;;
  14.  
  15. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  16.      The _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_ssss_cccc_hhhh_eeee_dddd_uuuu_llll_eeee_rrrr system call is used to get the scheduling policy
  17.      of the process specified by _p_i_d.  If _p_i_d is set to zero, then the
  18.      scheduling policy of the caller is returned.
  19.  
  20.      A process may obtain the scheduling policy of itself and any process
  21.      sharing the same real user ID [see _gggg_eeee_tttt_uuuu_iiii_dddd(2)].  To obtain the scheduling
  22.      policy of an unrelated process, the calling process must have the
  23.      CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT capability [see _c_a_p_a_b_i_l_i_t_y].
  24.  
  25.      If _p_i_d refers to a POSIX thread process [see _pppp_tttt_hhhh_rrrr_eeee_aaaa_dddd_ssss(3P)] then this call
  26.      retrieves the scheduling policy that is shared by process scope and bound
  27.      scope threads.
  28.  
  29.      _ssss_cccc_hhhh_eeee_dddd______gggg_eeee_tttt_ssss_cccc_hhhh_eeee_dddd_uuuu_llll_eeee_rrrr will fail if one or more of the following are true:
  30.  
  31.      [EINVAL]       The process specified by _p_i_d is not executing with a
  32.                     scheduling policy.
  33.  
  34.      [EPERM]        The calling process attempted to obtain the scheduling
  35.                     policy of an unrelated process and the caller does not
  36.                     have the CCCCAAAAPPPP____SSSSCCCCHHHHEEEEDDDD____MMMMGGGGTTTT capability.
  37.  
  38.      [ESRCH]        The process specified by _p_i_d does not exist.
  39.  
  40. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  41.      capability(4), sched_setparam(2), sched_getparam(2),
  42.      sched_setscheduler(2), sched_yield(2), sched_get_priority_max(2),
  43.      sched_get_priority_min(2), sched_rr_get_interval(2), sproc(2), fork(2),
  44.      getuid(2), pthreads(5)
  45.  
  46. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  47.      Upon successful completion, one of the following scheduling policies is
  48.      returned: SCHED_FIFO, SCHED_RR, SCHED_TS.  These scheduling policies are
  49.      described in _ssss_cccc_hhhh_eeee_dddd______ssss_eeee_tttt_ssss_cccc_hhhh_eeee_dddd_uuuu_llll_eeee_rrrr(2).
  50.  
  51.      Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to indicate the
  52.      error.
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  60.  
  61.  
  62.                                                                         PPPPaaaaggggeeee 1111
  63.  
  64.  
  65.  
  66.